Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Frontend - Login #27

Merged
merged 21 commits into from
Jan 8, 2025
Merged

Frontend - Login #27

merged 21 commits into from
Jan 8, 2025

Conversation

WishingWell13
Copy link
Contributor

@WishingWell13 WishingWell13 commented Dec 30, 2024

Info

Closes #21. (If there is no issue for this pull request yet, please create one or
delete this line if the pull request is for a very minor tweak).

Description

What changes did you make? List all distinct problems that this PR addresses. Explain any relevant
motivation or context.

Created frontend for login page

Changes

  • [Fill in here]

Type of Change

  • Patch (non-breaking change/bugfix)
  • Minor (non-breaking change which adds functionality)
  • Major (fix or feature that would cause existing functionality to not work as
    expected)
  • Documentation (A change to a README/description)
  • Continuous Integration/DevOps Change (Related to deployment steps, continuous integration
    workflows, linting, etc.)
  • Other: (Fill In)

If you've selected Patch, Minor, or Major as your change type, make sure to bump the version before merging in package.json!

Testing

I have tested that my changes fully resolve the linked issue ...

  • locally.
  • on the testing API/testing database.
  • with appropriate Postman routes. Screenshots are included below.

Checklist

  • I have performed a self-review of my own code.
  • I have followed the style guidelines of this project.
  • I have appropriately edited the API version in the package.json file.
  • My changes produce no new warnings.

Screenshots

Please include a screenshot of your Postman testing passing successfully.

Copy link

Thanks for contributing!
If you've made changes to the API's functionality, please make sure to bump the package
version—see this guide to semantic versioning for details—and
document those changes as appropriate.

@WishingWell13
Copy link
Contributor Author

Missing temp API stuff, if anyone has a reference please link

Copy link
Collaborator

@alexzhang1618 alexzhang1618 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we get some screenshots / screen recordings of what the page looks like?

client/src/app/page.module.scss Outdated Show resolved Hide resolved
Comment on lines +1 to +21
import styles from './style.module.scss';
import Error from '../../../public/assets/error.svg';
import { PropsWithChildren } from 'react';

interface AlertProps {
marginBottom: 0 | 1 | 1.5 | 2;
}

const Alert = ({ marginBottom, children }: PropsWithChildren<AlertProps>) => {
return (
<div className={styles.alert} style={{ marginBottom: `${marginBottom}rem` }}>
<div className="error">
<Error />
</div>

{children}
</div>
);
};

export default Alert;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we're doing font stuff here might as well just use Typography. Also, what's the difference between this and useToast from portal-v2? If it's similar, let's just use toasts

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

From the Figma it doesn't look like a pop up? Let me know if toasts can be non popup or if we want to change the error to a pop up

@WishingWell13
Copy link
Contributor Author

WishingWell13 commented Dec 30, 2024

Desktop
image

Desktop smaller window
image

(I'll reorder error message when I get home)

client/src/app/page.module.scss Outdated Show resolved Hide resolved
client/src/components/Alert/style.module.scss Outdated Show resolved Hide resolved
@WishingWell13
Copy link
Contributor Author

Copy link
Collaborator

@alexzhang1618 alexzhang1618 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just one nit

client/yarn.lock Outdated
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm if nothing changed in package.json, why is this getting updated? Would recommend taking a look or regenerating this

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unsure. Regenerated and still different.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this file used anywhere

README.md Outdated Show resolved Hide resolved
client/src/app/login/page.tsx Outdated Show resolved Hide resolved
@alexzhang1618 alexzhang1618 merged commit 1389d9a into main Jan 8, 2025
3 checks passed
@alexzhang1618 alexzhang1618 deleted the andy/login branch January 8, 2025 01:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Frontend - Login
3 participants